Best Practices for Event Orchestration

#1

What are the best practices when setting up new Event Orchestrations? When should new orchestrations be setup? How should they be categorized? (e.g. by team, by monitoring application)

#2

Hi Nathaniel,

Thanks for reaching out to us about this.

Looks like you had also emailed the support team about this and we have responded to that email.

Hope this helps and let me know if you have any other questions!

#3

Great question Nathaniel! There are many correct answers, so I will share a few of our common deployment and best practice patterns we use with customers.

  • Aligned with a business product, offering, service or application: All monitoring tools (or others like change events, CI/CD, security, etc.) are integrated into a single event orchestration and route/process incoming events and alerts to appropriate granular technical services in PagerDuty. Finer grained service event orchestration rules on the service can be used as needed on each service. This would be our best practice approach!
  • Aligned with a centralized monitoring tool: Send in all of your monitoring tool events/alerts into specific event orchestrations for that tool and route/process into granular technical services. Great when a central team owns the monitoring tool(s).
  • Aligned with a team/function: Send in all events/alerts from all tools in use by a specific team/function into an event orchestration owned by that team and route/process into that teams granular technical services. This approach works well in teams with a “full service ownership” operating model with that team owning all aspects of their PagerDuty configurations.
  • Central Admin Model - This might be a hybrid approach using any of the above where a central “tools team” oversees all aspects of integration, configuration and event/alert and user on-boarding into the PagerDuty environment. They may want to “lock down” end user configuration abilities in favor of centralized automation with an internal configuration management tool or process (eg Terraform) to ensure standards and best practices are followed and prevent configuration drift.

Feel free to reach out direct if you’d like to dive into any of these areas in more detail!

1 Like